Customer Specific Network Slicing

ABSTRACT

A system, device and method, for customer specific network slicing includes a VNO server, a first node, and a virtualized network. The VNO server executes computer instructions instantiating a solution manager engine which identifies a Solution, communicates the Solution to the first node, and upon acceptance of the Solution by the first node, instructs the virtualized network to couple the first node with a second node in accordance with the Solution. The virtualized network may include network function virtualization infrastructure and the Solution may include a slice of the virtualized network. The slice satisfies a Service Level Requirement (SLR), such as one that specifies a maximum latency for the slice. The SLR is specified in a Need received by the VNO server from the first node. The SLR is determined based upon an application program the first Node is at least one of currently executing and expected to later execute.

TECHNICAL FIELD

The technology described herein generally relates to devices, systems,and processes for facilitating customer specific networking slicing.

BACKGROUND

Various devices, systems and processes today enable network providers tomultiplex numerous virtualized and independent logical networks onto agiven physical network infrastructure. Such multiplexing is commonlyreferred to as “network slicing.” For a virtualized network, each“slice” is commonly a virtually isolated end-to-end network, operatingover various physical infrastructure components which couple two or morenodes (or other end points of a network) together. As used herein, a“node” can be any device, and/or applications, such as distributedapplications, virtualized applications and the like, that are executed,in whole or in part by a device, connected, directly or indirectly, suchas by a local area network (LAN), to a network. A slice is commonlytailored to fulfill various networking, communications, data storage,data processing and other requirements, as requested by a particularnode or nodes. Different requirements for different slices may requireuse of different logical and physical infrastructure components. Eachslice commonly has associated with it a service level requirement (SLR).An SLR may be pre-determined or specified in-advance and with respect toa given use and/or user of a given slice. The SLR influences physicalinfrastructure components utilized, how the virtualization of a givenlogical network occurs in the actual physical domain, and the like. Tofacilitate slicing various well-known concepts are commonly used, suchas software defined networks (SDNs), and network function virtualization(NFV). SDNs and NFVs facilitate scalable, flexible networks that operateusing a common network infrastructure. Virtualized networks, and slicesprovided to users therewith, are commonly dynamic in that they may useat any given time any selection of and/or combination of physicalinfrastructure components needed to satisfy a given SLR.

Typically, network slices are managed and operated by a virtual networkoperator (VNO), as used herein a VNO can be a mobile network operatorand/or a mobile virtual network operator, or the like. The VNO commonlycontracts with one or more physical network infrastructure providers.The physical infrastructure provider(s) may provide, for example, dataservers, communications switches, communications backbone elements suchas radio frequency, fiber optic, wired and other forms of communicationslinks, data hubs, and the like. Since physical infrastructure componentsuses, availabilities, capabilities, and the like vary over time, a VNOcommonly uses a logical component often referred to as an “orchestrator”to manage the physical infrastructure components utilized, at a giventime, by any given slice.

Today, network slicing is commonly provided today between VNOs andspecific enterprise customers and with regards to a particular program,given SLRs, and often on a predetermined and/or static basis. While suchprovisioning may satisfy predictable and commonly occurring needs forthe given enterprise customer, mechanisms are needed for providingnetwork slicing in view of dynamic SLR needs and/or in view of dynamic,ad hoc users, such as small business, individual users, applications, orthe like.

Further, network slicing today often results in inefficient allocationsof scare network resources. Being provided on a pre-determined, oftenstatic basis to given enterprise customers, such pre-allocated networkslices often do not fully utilize the potential of one or more logicaland/or underlying physical infrastructure components. Often, thenon-use, inefficient use, or limited use of one or more slicecapabilities may be undetermined, non-monitored, not realized, orotherwise under-utilized. Accordingly, network inefficiencies oftenoccur and usage gaps of permissible slices commonly arise. Thus, a needalso exists for identifying and allocating network slice usage gaps andfor utilizing logical and physical network resources more efficiently.

The various embodiments of the present disclosure address these andother needs.

SUMMARY

Various implementations are described of devices, systems, and processesfor facilitating customer specific network slicing.”

In accordance with at least one implementation of the presentdisclosure, a system of one or more computers may be configured toperform particular operations or actions by virtue of having software,firmware, hardware, or a combination of them installed on the systemthat in operation causes or cause the system to perform the actions. Oneor more computer programs may be configured to perform particularoperations or actions by virtue of including instructions that, whenexecuted by data processing apparatus, cause the apparatus to performthe actions. One general aspect includes a system that includes a VNOserver; a first node; and a virtualized network. The VNO server executesfirst computer instructions instantiating a solution manager enginewhich: identifies a Solution; communicates the Solution to the firstnode; and upon acceptance of the Solution by the first node, instructsthe virtualized network to couple the first node with a second node inaccordance with the Solution. Other embodiments of this aspect includecorresponding computer systems, apparatus, and computer programsrecorded on one or more computer storage devices, each configured toperform the actions of the methods.

Implementations may include one or more of the following features. Thevirtualized network further may include network function virtualizationinfrastructure. The Solution may include a slice of the virtualizednetwork. The Solution may provide the slice which satisfies a servicelevel requirement (SLR). The SLR may specify a maximum latency for theslice. The SLR may be specified in a Need received by the VNO serverfrom the first node. The SLR may be determined based upon an applicationprogram the first node is at least one of currently executing andexpected to later execute. The application program may specify at leastone of a data processing requirement and a data communicationrequirement. The application program may facilitate day trading. Theapplication program may facilitate real-time sports betting. The VNOserver may execute second computer instructions instantiating anartificial intelligence/machine learning (AIML) engine which: monitorsthe Solution; monitors the first node for a requested Need; andgenerates a future Solution to a future Need. The AIML engine mayidentify gaps in the virtualized network based upon at least one of theSolution, a past Solution, a future Solution, the requested Need, a pastNeed, and the future Need. The solution manager engine may identify afuture Need based upon an application program the first node is at leastone of currently executing and expected to later execute.Implementations of the described techniques may include hardware, amethod or process, or computer software on a computer-accessible medium.

One general aspect includes a node. The node also includes a centralprocessing unit (CPU); where the CPU executes computer instructionsinstantiating a need engine which: generates a Need; communicates theNeed to a VNO server; receives a Solution to the Need from the VNOserver; and communicates at least one of an acceptance, a rejection, anda revised Solution to the VNO server. Other embodiments of this aspectinclude corresponding computer systems, apparatus, and computer programsrecorded on one or more computer storage devices, each configured toperform the actions of the methods.

Implementations may include one or more of the following features. TheNeed identifies at least one service level requirement (SLR) for acommunicative coupling of the node with a second node over a virtualizednetwork. The Solution identifies a slice of the virtualized network; andwhere the Solution identifies whether the SLR identified in the Need maybe satisfied by the slice of the virtualized network. The SLR mayinclude a bandwidth requirement. The bandwidth requirement may arisewith respect to a telemedicine application. Implementations of thedescribed techniques may include hardware, a method or process, orcomputer software on a computer-accessible medium.

One general aspect includes a method for allocating virtualized networkresources. The method also includes receiving, at a VNO server and froma first node, a Need request; determining whether the Need request maybe satisfied by a present Solution; if the need request may be satisfiedby the present Solution, assigning the present Solution to the firstnode; and communicatively coupling the first node with at least onesecond node using a slice of a virtualized network specified by thepresent Solution. The method may also include, if the need requestcannot be satisfied by the present solution, generating a new Solution.Other embodiments of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.

Implementations may include one or more of the following features. TheNeed request may identify a service level requirement (SLR). The presentSolution satisfies the SLR. The new Solution identifies at least onealternative to the SLR. The SLR may specify at least one of a maximumlatency, a bandwidth, a security requirement, and a routing requirement.Implementations of the described techniques may include hardware, amethod or process, or computer software on a computer-accessible medium.

BRIEF DESCRIPTION OF THE DRAWINGS

The features, aspects, advantages, functions, modules, and components ofthe devices, systems and processes provided by the variousimplementations of embodiments of the present disclosure are furtherdisclosed herein regarding at least one of the following descriptionsand accompanying drawing figures. In the appended figures, similarcomponents or elements of the same type may have the same referencenumber and may include an additional alphabetic designator, such as 108a-108 n, and the like, wherein the alphabetic designator indicates thatthe components bearing the same reference number, e.g., 108, sharecommon properties and/or characteristics. Further, various views of acomponent may be distinguished by a first reference label followed by adash and a second reference label, wherein the second reference label isused for purposes of this description to designate a view of thecomponent. When the first reference label is used in the specification,the description is applicable to any of the similar components and/orviews having the same first reference number irrespective of anyadditional alphabetic designators or second reference labels, if any.

FIG. 1 is a schematic illustration of a system for facilitating customerspecific network slicing and in accordance with at least oneimplementation of the present disclosure.

FIG. 2 illustrates a server configured for use in facilitating customerspecific network slicing and in accordance with at least oneimplementation of the present disclosure.

FIG. 3 illustrates a node configured for use in facilitating customerspecific network slicing and in accordance with at least oneimplementation of the present disclosure.

FIG. 4 illustrate a method for use in facilitating customer specificnetwork slicing and in accordance with at least one implementation ofthe present disclosure.

DETAILED DESCRIPTION

Various implementations of the present disclosure describe devices,systems, and processes for facilitating customer specific networkslicing. As used herein, “customer specific network slicing” refers tothe providing of one or more network slices, wherein each slice (orcombination of slices) is tailored to satisfy a given node's ad hoc“communication needs.”

As used herein, a “communication need” is one or more characteristicsfor a given, ad hoc use of one or more logical and/or physical networkelements between a first node and at least one second node. Thecommunication need may also identify a data processing, data storage,data rendering, or other data operation requirement (herein,individually and collectively, a “data need”). The communication needand/or data need (herein, the “Need”) may be specified automatically(for example, by an application program having minimum SLR and otherrequirements), semi-automatically (for example, by a user selection ofan option from a range of acceptable or available SLRs), or manually(for example, by a user individually specifying each of one or more SLRsfor a given connection or set of connections).

A Need often arises on an ad hoc basis, in that a given one or more SLRsmay be requested for a given set of data to be communicated, for a givendata operation to be performed, for a given time-period, or otherwise.That is, unlike existing arrangements between enterprise customers andVNOs which establish continually available network connectionssatisfying pre-determined SLRs, a Need is temporary as the Need existsonly as long as an amount of time necessary, per a given SLR, tocommunicate a given quantity of data, perform a data processing, storageand/or other data operation, or otherwise accomplish some dataprocessing and/or communication action. The Need arises and exists whena first node has one or more SLRs that are to be satisfied for a giventransaction or a series of transactions, where such transactions are notpre-planned or pre-determined.

A non-limiting example of a Need is a stock day trader who commonlymaintains a connection between their computing device, a first node, anda broker's computing device, a second node. For normal transactions,non-specified SLRs may be acceptable—that is, the day trader's Needs maybe described as being generic. However, when an urgent, or timesensitive trade is to be transacted, for example to complete a complextrade (or series thereof), the day trader may seek to acquirecommunications services that meet certain defined SLRs, such as thecommunications occur without exceeding a maximum network latency, usinga certain bandwidth, having certain security characteristics, routingrequirements such as avoiding foreign data servers, or otherwise.

Other non-limiting examples of Needs may include real-time online sportsbetting, telemedicine, banking transactions, cryptocurrency mining, andothers. Any use of a communications network, a communications resources,a data processing resource, a remotely controlled device, system orprocess, or otherwise may be considered a Need.

A “Solution” is one or more fulfillments of a given Need. A Solution maybe characterized as a satisfying of one or more SLRs in response to agiven Need. A Solution may be associated with an identified VNO ormultiple VNOs. A Solution may be uniquely provided by a given VNO,common to multiple VNOs, be an aggregate of solutions provided bymultiple VNOs, or otherwise. A Solution may be identified on aselectable listing, formed based upon a selection of one or more SLRrequirements from a menu or other ordering system, or otherwiseidentified and selected by a user. A Solution may be allocated on afirst come, first-to-purchase, auction, bidding, or other process. ASolution may be associated with a static pricing model where a specifiedSLR is equated with a given pricing structure, model, or the like.Improvements or degradations in one or more SLRs may result in amodification of the given pricing structure. A Solution may beassociated with a dynamic pricing model where pricing of a givenSolution may dynamically vary based upon each SLR selected, then arisingnetwork characteristics, anticipated network characteristics, andotherwise. For example, a day trader requesting certain SLRs when amarket has a high trading volume may result in a dynamically adjustedprice for a given SLR that is higher than when the stock market isslow-moving or has a reduced trading volume.

A Solution may be configured to satisfy one or more SLRs based uponhistorical customer uses, then arising customer specific uses,dynamically, or otherwise. Artificial Intelligence processes and machinelearning technologies (herein, individually and collectively “AIML”) maybe used to identify Solutions, the SLRs fulfilled by the Solution, thepricing of the Solution, and/or other use terms associated therewith.For example, AI may be used to determine Needs commonly desired andSolutions available by online gamblers during certain sporting events,such as professional American football games. Such AI processes may beconfigured to package Solutions, for manual, semi-automatic and/orautomatic selection and use by gamblers, via gambling applications,websites, or the like.

As used herein, a reference to “Cloud” includes references to cloudcomputing, cloud storage, cloud communications, and/or other technologyresources which a user may not actively manage the providing or use ofsuch resources. A use of a Cloud resource may be private (limited tocertain users and/or uses), public (available for many users and/oruses), hybrid, dedicated, non-dedicated, or otherwise. It is to beappreciated that any device or system of the various embodiments of thepresent disclosure may use Cloud resources to provide one or moreSolutions.

“Substantially simultaneous” means without incurring a perceptible delaybetween a first event or condition, such as a submission of a traderequest, and a second event or condition, such as an execution of suchtrade request by a broker's computing systems. It is to be appreciatedthat substantial simultaneity will vary based upon the characteristicsof the sending and receiving nodes. For example, an action issubstantially simultaneous with respect to node associated with a humanuser when an imperceptible human delay occurs. By another example, anaction is substantial simultaneous with respect to a node associatedwith an automated or machine process, such as a computing process, whenan action is performed without a delay greater than as required to meeta given SLR.

“Separate” means a first node may be physically or virtually separatedfrom one or more second nodes. Such separation may occur geographically,wherein a first node is in a different room, building, city, state, orcountry than one or more second nodes. The separation may occurvirtually by use of distinct logical networks, distinct physicalnetworks, or otherwise.

“Content” refers to any information that may be presented, using asuitable presentation device, to a user in a humanly perceptible format.Non-limiting examples of content, include video, television programs,audio programs, speeches, concerts, gaming, or otherwise. Content mayoriginate from any source, including live, augmented reality, virtualreality, computer generated, or otherwise. Content may be presented to agiven user, at a node, using any “user device” (as described below).Content may be presented to one or more users real-time or otherwise.Content may be stored, transmitted, processed or otherwise manipulatedin non-humanly perceptible formats that may be converted, by known andlater arising devices, systems and methods, into humanly perceptibleinformation presented by a suitable presentation device. Currentembodiments of such presentation devices are well known any suitableknown or later arising presentation device may be used for contentpresentation to users.

As shown in FIG. 1 , one implementation of a system 100 for facilitatingcustomer specific network slicing includes two or more nodes, such as afirst node 102-1 and an Nth node 102-N. As used herein, a “node” 102 isany device configurable to communicate data using a network, directly orindirectly, to another node. A node 102 may be a stand-alone device,such as a human user's laptop computer, personal computer, smartphone,gaming device, or the like. A node 102 may be a thread operating on acomputing system having a multiple threaded operating system, such asthe WINDOWS 10 operating system, LINUX, APPLE OS, ANDROID, and others. Anode 102 may be an application program executing on a computing device,a web service, or otherwise. An Application Program Interface (API) maybe used by a node 102 to support an implementation of the presentapplication. A node 102 may occur in the virtual domain and/or in thephysical domain. A node 102 may be associated with a human user, amachine process executing on one or more computing devices, an API, aweb service, instantiated on the Cloud, distributed across multiplecomputing devices, or otherwise.

As shown in FIG. 1 , the system 100 includes at least two nodes 102-1and 102-N configured to communicate data there between. For otherimplementations, any number of nodes may be used and Needs and Solutionsexpressed and fulfilled, respectively, there between. Further, it is tobe appreciated that the Needs and Solutions may be bi-directional,uni-directional, or otherwise. For example, a day trader seeking tocommunicate an urgent trade request to the broker's system may have aNeed for SLRs with as little latency as is physically possible(considering the speed of light, distance, and other physicallimitations). A return communication by the broker confirming the trademay not require the same level of SLRs. Accordingly, Needs and Solutionsmay be requested and fulfilled based upon types of communicationsneeded, data processing urgency required, nature of requester, andotherwise.

The system 100 includes a VNO server 104. The server 104 iscommunicatively coupled, by a server link 114 to a network 106,including network function virtualization infrastructure 110, and byrespective first node link 112 and second to nth node links 118-2/N, tothe various nodes 102-1/N. The node links 112 and 118-2/N may betransient links, existing only as necessary to establish, maintain,monitor, deconstruct, or otherwise one or more links satisfying one ormore Needs and in accordance with one or more SLRs. The server 104 mayalso be communicatively coupled by a database link 116 to a database108. The links 112-118 may utilize any form of communicationsarchitecture, protocols, topologies, technologies, or otherwise. Thenodes 120 may be further coupled to each other for the exchange of datatherebetween. The links 112-120 may utilize the Cloud, be direct links,use one or more networks, or otherwise.

The network 106 includes physical data processing and communicationcomponents. Network function virtualization infrastructure 110facilitates adaption, control and other operations of physical networkcomponents. Non-limiting examples of physical network components includedata processing and communications components including computerservers, blade servers, switches, routers, encryption/decryption andother data security components, data storage and warehousing components,communication links such as those provided by wired connections,wireless connections including micro-wave, 3G/4G/5G, WIFI, and othertypes, satellite connections, fiber optic connections, and othercomponents. Any known or later arising physical data processing and/orcommunications components may be utilized.

As is well known, physical data processing and communications componentsmay be logically defined, organized and utilized as a network functionvirtualization infrastructure 110. The virtualization of data processingand communications component infrastructures is well known in the artand any known or later arising topologies, approaches, methods,protocols, or the like for such virtualization may be utilized.

For at least one implementation, the network function virtualizationinfrastructure 110 may include commonly known components such asorchestrators, network function virtualization managers, virtualizationinfrastructure managers, and other components. The virtualizationinfrastructure 110 facilitates the providing of Solutions to nodes 102by configuring one or more physical network resources to provide slicesand other physical elements that satisfy one or more Needs. The networkfunction virtualization infrastructure 110 may be configured to utilizeany known and/or later arising network virtualization components. Othernetwork function virtualization infrastructure 110 applications,components, APIs, and otherwise may be used in a given implementation ofthe present disclosure.

VNO Server 104

As shown in FIGS. 1 and 2 , the VNO server 104 may include and/or becommunicatively coupled to a server central processing unit (CPU) 202.The server CPU 202 may be provided by any processing device capable ofexecuting one more computer executable instructions (herein, a “computerinstruction”) which, in accordance with an implementation of the presentdisclosure, facilitates one or more data processing operationsincluding, and not limited to, one or more computer engines such as aSolution manager engine 202A, and an AIML engine 202B (such computerengines are further described below). One or more of the computerengines 202-AB may be combined, included, not included, distributedacross one or more devices, such as being provided in whole or in partby one or more nodes 104, network components 106, or otherwise.

The server CPU 202 may include one or more physical and/or logicalcomponents configured for such data processing operations. The serverCPU 202 may include one or more hardware processors, such as 32-bit and64-bit central processing units, multi-core ARM based processors,microprocessors, microcontrollers, and otherwise. The processors may bephysically and/or virtually instantiated. The processors provided by theserver CPU 202 may be localized, distributed, Cloud based, or otherwiseprovided. The computer instructions may include instructions forexecuting one or more application programs, APIs, software computerengines, and/or other processes configured to perform computerexecutable operations (herein, “engines”). Such engines may arise in anycomputing configuration including, and not limited to, local, remote,distributed, blade, virtual, or other configurations and/or systemsconfigured for use in support of an implementation of one or moreembodiments of the present disclosure.

Solution Manager Engine 202A

The VNO server 104 may execute a Solution manager engine 202A. TheSolution manager engine 202A facilitates management of Solutions. TheSolution manager engine 202A may be configured to manage presentation ofSolutions to a node 102 and the acquisition of usage rights to aSolution selected by a node 102. Using user data 304A, the Solutionmanager engine 202A may identify Solutions that are pre-configured tosatisfy a user Need. For example, user data 304A may identify anapplication a node 102 is currently executing, data processing and/ordata communication requirements for such application, any userpreferences for prioritization of data requirements based on anexecuting application, user bidding preferences associated with a node'sacquiring of rights in a Solution, and otherwise. Based on such userdata 304A, the Solution manager engine 202A may identify one or moreSolutions to a given node for a then existing Need and/or for a futurearising Need. Such Solution(s) may specify one or more SLRs satisfied bythe Solution, identify one or more slices supported by the Solution,identify any upgrades/downgrades in SLRs that may be available andprovide other options for a node 102 to customize a Solution.

As shown in FIG. 4 and for at least one implementation, the Solutionmanager engine 202A may be configured to: receive a Need request from anode 102 (Operation 402); determine whether the Need can be satisfied bya present Solution (Operation 404); if so, assign the Solution to thenode 102 for use thereby at the relevant time (Operation 406); at therelevant time, communicatively couple the first node with the secondnode using a slice of the virtualized network specified by the presentSolution (Operation 408); and if a presently identified Solution is notavailable and/or capable of satisfying the Need, the Solution managerengine 202A may be configured to generate a new Solution (Operation410).

For at least one implementation the new Solution may satisfy one or moreSLRs. Such SLRs may be specified by the given Need and/or determined bythe Solution manager engine 202A in response to the given actual and/oranticipated Need. As discussed above, the Solution may satisfy acommunication need, a data need, both a communication need and a dataneed, and/or other forms of Needs.

For at least one implementation, the Solution manager engine 202A maycommunicate one or more Solutions to a node 102. The Solution(s) may becommunicated in a node processable format, such as in a data formatwhich a node 102 is configured to receive, process and act upon. TheSolution may be communicated in a secure format, such that informationidentifying protocols, security keys, links to be utilized, and/or otherinformation identifying a slice and/or a characteristic of a Solutionmay be accessible only by the intended Node(s).

For at least one implementation, the Solution manager engine 202A may beconfigured to communicate a Solution to node 102, such that the node 102can process the data provided by the Solution and present one or moreSolutions to a user in a humanly perceptible format. For example, a node102 may be configured to present received Solutions in a graphical,tabular, or other data format where multiple Solution options may bepresented and selected by a user, using a corresponding user inputdevice. For another example, a node 102 may be configured to presentreceived Solutions in a ranked order, price ordered, timeliness orders,SLR ordered, or any other format to facilitate user contemplation of theSolutions provided and selection of one more Solutions by the user.

For at least one implementation, the Solution manager engine 202A may beconfigured to predict future Needs for a given node 102 based upon userpreferences, user demographic information, user psychographicinformation, historical node Needs, and other data. Such data may beprovided to and/or otherwise acquired by the VNO server 104 and storedas user data 204A and/or Solution data 204B. For an implementation,Solution data 204B may include data identifying past Solutions acceptedby a given node 102, Needs which the Solution fulfilled, application(s)used with the Solution, and other information pertinent to thegeneration, presentation, management, and accounting for Solutions inview of one or more Needs.

For an implementation, the Solution manager engine 202A may beconfigured to facilitate a reservation system whereby a given node 102identifies to the VNO server 104 a future Need and reserves a futureSolution for such future Need. For example, a user of a node 102 that isplanning on participating in real-time sports betting for a futureoccurring sporting event may desire to reserve in advance, and for alimited time/specific event purpose, one or more Solutions at and/orabout the time of the sporting event.

The Solutions manager engine 202A may be configured to cooperate withother engines provided by the VNO server 104 including, but not limitedto, the AIML engine 202B.

The Solutions manager 202A may be configured to use: Solution data 204B,which identifies one or more Solutions; Need data 204C, which identifiesone or past, present or future Needs identified by one or more nodes102; pricing data 204D, which identifies pricing options for one or moreSolutions, where such pricing may be provided on an SLR basis, a slicebasis, or otherwise; and any other data 204E in generating, providing,tracking, monitoring, or otherwise facilitating Solutions to Needs.

For at least one implementation the Solution manager engine 202A may beconfigured to include APIs configured for use with one or more networkfunction virtualization infrastructure 110 components, applications, orotherwise.

AIML Engine 202B

The VNO server 104 may execute an AIML engine 202B. The AIML engine 202Bmonitors past and currently occurring Needs and Solutions and generatesfuture Solutions for anticipated future Needs.

For at least one implementation, the AIML engine 202B may be configuredto identify gaps in the network 106, where a network gap is an absenceof a Solution to a given Need. For example, a network 106 may not beconfigurable to offer a Solution satisfying one or more SLRs for a givenNeed. The AIML engine 202B may be configured to identify such gap andrecommend suggestions to alleviating such gap by one or more Solutionsand/or by adjusting one or more SLRs to provide a Solution that is moreresponsive to a given current or anticipated future Need. For example,the sporting event referenced above may be expected to generatesignificant interest by multiple nodes in Solutions satisfying certainSLRs. The AIML engine 202B may be configured to recognize that given theSLRs typically specified, the network 106 may be capable of providingSolutions satisfying such SLRs to only a limited number of nodes 102.However, the AIML engine 202B may be configured to recognize that asecond Solution satisfying a second set of SLRs may be provided to alarger selection of nodes 102 and thereby addressing the Needs of thelarger selection of nodes 102 but with a limited, if any impact upon theactual performance of a communication need, and/or a data need asaddressed by the second Solution.

Server Data Storage 204

The server CPU 202 may be communicatively coupled by a server data bus214, or similar structure, to a server data storage 204, which may alsobe referred to as a “computer readable storage medium.” The server datastorage 204 may be a single storage device, multiple storage devices, orotherwise. The server data storage 204 may be provided locally with theVNO server 104 or remotely, such as a data storage service provided onthe Cloud, by the database 108, and/or otherwise. Storage of dataincluding, and not limited to, user data 204A, Solution data 204B, Needdata 204C, pricing data 204D, and other data 204E may be managed by astorage controller (not shown) or similar component.

It is to be appreciated that a storage controller manages the storing ofdata and may be instantiated in one or more of the server data storage204, the server CPU 202, on the Cloud, on the database 108, orotherwise. Any known or later arising storage technologies may beutilized. Non-limiting examples of devices that may be configured foruse as server data storage 204 include electrical storage devices, suchas EEPROMs, random access memory (RAM), Flash drives, and solid-statedrives, optical drives such as DVDs and CDs, magnetic storage devices,such as hard drive discs, magnetic drives, magnetic tapes, memory cards,such as Compact Flash (CF), Secure Digital (SD) cards, Universal SerialBus (USB) cards, and others.

Available storage provided by the server data storage 204 may bepartitioned or otherwise designated by the storage controller, orotherwise, as providing for permanent storage and temporary storage.Non-transient data, transient data, computer instructions, or the likemay be suitably stored in the server data storage 204 for any amount oftime used to execute one or more computer instructions. While being usedfor execution of a computer instruction, such data is herein consideredto be non-transient. While stored by the storage device, data is hereinconsidered to be non-transient. As used herein, permanent storage isdistinguished from temporary storage, with the latter providing alocation for temporarily storing data, variables, or other instructionsused for a then arising data processing operations. A non-limitingexample of a temporary storage device is a memory component providedwith and/or embedded onto a processor or integrated circuit providedtherewith for use in performing then arising data calculations andoperations. Accordingly, it is to be appreciated that a reference hereinto “temporary storage” is not to be interpreted as being a reference totransient storage of data. Permanent storage and/or temporary storagemay be used to store transient and non-transient computer instructionsand other data.

The VNO server 104 may be any computing device capable of facilitatingone or more of the operations described herein and/or otherwise providedby an implementation of the present disclosure.

Server Power Supply 206

The VNO server 104 may be configured to include a server power supply206. The server power supply 206 may include any known or later arisingtechnologies which facilitate the storage, supplying, transforming, orother use of electrical energy. Non-limiting examples of suchtechnologies include batteries, power converters, inductive chargingcomponents, transformers, line-power components, solar power components,and otherwise.

Server Security 208

The VNO server 104 may be further configured to include a serversecurity component 208. The server security component 208 may beprovided as a hardware security component, a software executed securitycomponent, and/or a combination thereof. Security components are wellknown in the art and may include any known or later arising securityhardware and/or software components, including computer instructions, orcombinations thereof, that are configured to secure content,communications, restrict access to devices, processes, components, anddata therewith, and otherwise. The server security component 208 may beused to facilitate secure transmission, processing, storage, andotherwise of any data used in accordance with an implementation of thepresent disclosure.

Server User Interface 210

The VNO server 104 may be further configured to include a server userinterface 210. The server user interface 210 may include any known orlater arising human to device interface components, processes andtechnologies. User interfaces are well-known in the art and non-limitingexamples include interfaces facilitating human to device communicationof information in any form including include audible inputs (such asspoken commands) and outputs (generated sound), visible inputs (such aseye tracking and facial recognition) and outputs (such as visible imagespresented on a display device, LEDs, or otherwise), touch inputs (suchas on a trackpad, touch screen or otherwise), touch feedback (such asvibrations or other movements), gesture tracking, and otherwise. Theserver user interface 210 may be coupled to and/or include the one ormore presentation devices (not shown). The presentation devicesfacilitate interactions between a user thereof and the VNO server 104.Non-limiting examples of presentation devices include speakers,displays, and others.

Server Communications Interface 212

The VNO server 104 may be further configured to include servercommunications interfaces 212. The server communications interfaces 212may be configured to use any known or later arising communicationsand/or networking technologies which facilitate use of the network 106(as further described below). Communication interfaces are well-known inthe art and non-limiting examples include Ethernet cards, USB andstorage medium interface cards, radio frequency transceivers, andothers.

Nodes 102

Referring again to FIG. 1 and as shown in FIG. 3 , for at least oneimplementation of customer specific network slicing, the system 100includes at least a first node 102-1 communicating with a second node,such as the Nth node 102-N. The system includes one or more additionalnodes.

The nodes 102 may be similarly configured to the VNO server 104 toinclude one or more processors, data storage, user interface, powersupplies, security, and communications interface components.Non-limiting examples of nodes 102 include smartphones, laptopcomputers, tablet computing devices, desktop computers, smarttelevisions, smart glasses, virtual reality glasses, augmented realityglasses, earbuds/headphones and other audible output devices,application programs, web servers, and other devices.

Node CPU 302

More specifically, and as shown in FIG. 3 , the nodes 102 may be includea node CPU 302. The node CPU 302 may be provided by any processingdevice capable of executing one more computer instructions which, inaccordance with an implementation of the present disclosure, facilitatesone or more data processing operations including, and not limited to,one or more computer engines such as a slice engine 302A, and anapplication engine 302B (such computer engines are further describedbelow). One or more of the computer engines 302-AB may be combined,included, not included, distributed across one or more devices, such asbeing provided in whole or in part by one or more nodes 104, networkcomponents 106, or otherwise.

The node CPU 302 may include one or more physical (as compared tological) components configured for such data processing operations. Thenode CPU 302 may include one or more hardware processors, such as 32-bitand 64-bit central processing units, multi-core ARM based processors,microprocessors, microcontrollers, and otherwise. The processorsprovided by the node CPU 302 may be localized, distributed, Cloud based,or otherwise provided. The computer instructions may include one or moreengines. Such engines may arise in any computing configurationincluding, and not limited to, local, remote, distributed, blade,virtual, or other configurations and/or systems configured for use insupport of an implementation of one or more embodiments of the presentdisclosure.

For at least one implementation, the node CPU 302 may be configured toimplement a Need engine 302A.

Need Engine 302A

A node 102 may execute a Need engine 302A. The Need engine 302Afacilitates management of Needs and Solutions. The Need engine 302A maybe configured to generate a Need, manage communication of a Need to theVNO server 104, receive Solutions from the VNO server 104, communicateacceptance of a Solution to the VNO server 104, and perform otheroperations pertaining to Need and Solutions.

For at least one implementation, the Need engine 302 may be configuredto acquire, from a VNO server 104, usage rights to a Solution selectedby a node 102. Such usage rights may be communicated by the node 102,

and/or by the VNO server 104, to one or more of the network functionvirtualization infrastructure components 110 which facilitate use of thenetwork 106 by the node 102.

For at least one implementation, the Need engine may be configured toutilize user data 304A, which may include indications of applicationscurrently in use and/or likely to be in use at a later time, the Needengine 302A may identify present and/or future Needs. User data 304A mayalso include information indicating a user's preferences, such aspricing limits (min. and max.), security requirements, SLRs, applicationprograms available, web services used, connectivity data, such as thenodes 102 connectivity to network infrastructure, such as web servers,switches and the like, processing capabilities of the node 102, andother user/node specific data.

For at least one implementation, user data 304A may identify anapplication a node 102 is currently executing, data requirements forsuch application, any user preferences for prioritization of datarequirements based on an executing application, user bidding preferencesassociated with a node's acquiring of rights in a Solution, andotherwise. Based on such user data 304A, the Need engine 302A mayidentify one or more Solutions, as identified by a VNO server 104, or athen existing Need and/or for a future arising Need. Such Solution(s)may specify one or more SLRs satisfied by the Solution, identify one ormore slices supported by the Solution, identify any upgrades/downgradesin SLRs that may be available and provide other options for a node 102to customize a Solution.

The Need engine 302A may be configured to utilize Solution data 304B.The Solution data 304B may be populated based upon information receivedfrom a VNO server 104, based on past Solutions selected, modified, orrejected, and/or other information. The Need engine 302A may manage thepresentation, selection, and monitoring of Solutions.

The Need engine 302A may be configured to utilize Need data 304C. TheNeed data 304C may identify SLRs based upon user preferences,application requirements, anticipated activities, such as real-timesports betting, day-trading, or the like, and/or based upon otherinformation. Need data 304C may be used in preparing and transmitting aNeed request to a VNO server when a pre-packaged Solution is notavailable or does not satisfy a current Need.

For at least one implementation, the Need engine 302A may be configuredto receive a Need request from a user of the given node 102, determinewhether the Need can be satisfied by a presently identified Solution,and if so, request assignment/reservation of the Solution, by the VNOserver 104, to the node 102 for use thereby and at the relevant time.When a presently identified Solution is not available and/or capable ofsatisfying the Need, the Need engine 302A may be configured tocommunicate a Need request, which requests generation of a new Solutionby a VNO server 104. The new Need request may identify one or more SLRsto be satisfied by a Solution. Such SLRs may be specified by the givenNeed and/or determined by a VNO server 104 in response to the givenactual and/or anticipated Need. As discussed above, the Solution maysatisfy a communication need, a data need, both a communication need anda data need, and/or other forms of Needs. A Need request may specify oneor more of such communication needs, data needs, both, and other needs.

For at least one implementation, the Need engine 302A may be configuredto receive and present one or more Solutions to a user of a node 102.The user may be a person, a machine process, an Artificial Intelligenceentity, or any other entity capable of receiving and selecting aSolution. The Need engine 302A may be configured to automatically,semi-automatically, and/or manually select a Solution. The Solution(s)may be received in a node processable format, such as in a data formatin which a node 102 is configured to receive, process and act upon. TheSolution may be received in a secure format, such that informationidentifying protocols, security keys, links to be utilized, and/or otherinformation identifying a slice and/or a characteristic of a Solutionmay be accessible only by the intended Node(s).

For at least one implementation, the Need engine 302A may be configuredto receive a Solution, process the data provided by the Solution andpresent one or more Solutions to a user in a humanly perceptible formatvia the user interface 310 and one or more user interface devices, suchas speakers, monitors, or otherwise. For example, a node 102 may beconfigured to present received Solutions in a graphical, tabular, orother data format where multiple Solution options may be presented andselected by a user, using a corresponding user input device. For anotherexample, a node 102 may be configured to present received Solutions in aranked order, price ordered, timeliness orders, SLR ordered, or anyother format to facilitate user contemplation of the Solutions providedand selection of one more Solutions by the user.

For at least one implementation, the Need engine 302A may be configuredto predict future Needs for a given node 102 based upon userpreferences, user demographic information, user psychographicinformation, historical node Needs, as stored in the node data storage304 as, for example, Need data 304C, and other data. Such data may beprovided to and/or otherwise acquired by the node 102 and stored as userdata 304A, Solution data 304B, and/or Need data 304C. For animplementation, Solution data 204B may include data identifying pastSolutions accepted by a given node 102, Needs which the Solutionfulfilled, application(s) used with the Solution, and other informationpertinent to the generation, presentation, management, and accountingfor Solutions in view of one or more Needs.

For an implementation, the Need engine 302A may be configured tofacilitate a reservation system whereby a given node 102 identifies tothe VNO server 104 a future Need and reserves a future Solution for suchfuture Need. For example, a user of a node 102 that is planning onparticipating in real-time sports betting for a future occurringsporting event may desire to reserve in advance, and for a limitedtime/specific event purpose, one or more Solutions at and/or about thetime of the sporting event.

The Need engine 202A may be configured to cooperate with other enginesprovided by the node. For at least one implementation the Need engine302A may be configured to include APIs configured for use with one ormore network function virtualization infrastructure 110 components,applications, or otherwise.

Node Data Storage 304

The node CPU 302 may be communicatively coupled, by a node data bus 314or similar structure, to a node data storage 304, which may also bereferred to as a “computer readable storage medium.” The node datastorage 304 may be a single storage device, multiple storage devices, orotherwise. The node data storage 304 may be provided locally with agiven node 102 or remotely, such as a data storage service provided onthe Cloud, by the database 108, and/or otherwise. Storage of dataincluding, and not limited to, user data 304A, Solution data 304B, Needdata 304C, and other data 304D may be managed by a storage controller(not shown) or similar component.

It is to be appreciated that a storage controller manages the storing ofdata and may be instantiated in one or more of the node data storage304, the node CPU 302, on the Cloud, on the database 108, or otherwise.Any known or later arising storage technologies may be utilized.Non-limiting examples of devices that may be configured for use as nodedata storage 304 include electrical storage devices, such as EEPROMs,random access memory (RAM), Flash drives, and solid-state drives,optical drives such as DVDs and CDs, magnetic storage devices, such ashard drive discs, magnetic drives, magnetic tapes, memory cards, such asCompact Flash (CF), Secure Digital (SD) cards, Universal Serial Bus(USB) cards, and others.

Available storage provided by the node data storage 304 may bepartitioned or otherwise designated by the storage controller, orotherwise, as providing for permanent storage and temporary storage.Non-transient data, transient data, computer instructions, or the likemay be suitably stored in the node data storage 304 for any amount oftime used to execute one or more computer instructions. While being usedfor execution of a computer instruction, such data is herein consideredto be non-transient. While stored by the storage device, data is hereinconsidered to be non-transient. As used herein, permanent storage isdistinguished from temporary storage, with the latter providing alocation for temporarily storing data, variables, or other instructionsused for a then arising data processing operations. A non-limitingexample of a temporary storage device is a memory component providedwith and/or embedded onto a processor or integrated circuit providedtherewith for use in performing then arising data calculations andoperations. Accordingly, it is to be appreciated that a reference hereinto “temporary storage” is not to be interpreted as being a reference totransient storage of data. Permanent storage and/or temporary storagemay be used to store transient and non-transient computer instructionsand other data.

The node 102 may be any computing device capable of facilitating one ormore of the operations described herein and/or otherwise provided by animplementation of the present disclosure.

Node Power Supply 306

The node 102 may be configured to include a node power supply 306. Thenode power supply 306 may include any known or later arisingtechnologies which facilitate the storage, supplying, transforming, orother use of electrical energy. Non-limiting examples of suchtechnologies include batteries, power converters, inductive chargingcomponents, transformers, line-power components, solar power components,and otherwise.

Node Security Component 308

The node 102 may be further configured to include a node securitycomponent 308. The node security component 308 may be provided as ahardware security component, a software executed security component,and/or a combination thereof. Security components are well known in theart and may include any known or later arising security hardware and/orsoftware components, including computer instructions, or combinationsthereof, that are configured to secure content, communications, restrictaccess to devices, processes, components, and data therewith, andotherwise. The node security component 308 may be used to facilitatesecure transmission, processing, storage, and otherwise of any data usedin accordance with an implementation of the present disclosure.

Node User Interface 310

The node 102 may be further configured to include a node user interface310. The node user interface 310 may include any known or later arisinghuman to device interface components, processes and technologies. Userinterfaces are well-known in the art and non-limiting examples includeinterfaces facilitating human to device communication of information inany form including include audible inputs (such as spoken commands) andoutputs (generated sound), visible inputs (such as eye tracking andfacial recognition) and outputs (such as visible images presented on adisplay device, LEDs, or otherwise), touch inputs (such as on atrackpad, touch screen or otherwise), touch feedback (such as vibrationsor other movements), gesture tracking, and otherwise. The node userinterface 310 may be coupled to and/or include the one or morepresentation devices (not shown). The presentation devices facilitateinteractions between a user thereof and the node 102. Non-limitingexamples of presentation devices include speakers, displays, and others.

Node Communications Interface 312

The node 102 may be configured to include node communications interfaces312. The node communications interfaces 312 may be configured to use anyknown or later arising communications and/or networking technologieswhich facilitate use of the network 106 and/or the network functionvirtualization infrastructure 110. Communication interfaces arewell-known in the art and non-limiting examples include Ethernet cards,USB and storage medium interface cards, radio frequency transceivers,and others.

Network 106

As shown in FIG. 1 and for at least one implementation, the system 100includes a network 106 that communicatively couples a node 102 with theVNO server 104 and communicatively couples the first node 102-1 with onemore additional nodes 102-N.

For at least one implementation, nodes 102 may be directly or indirectlycoupled. The network 106 may utilize any known and/or later arisingcommunications and/or networking technologies, standards, protocols orotherwise. Non-limiting examples of such technologies include packetswitch and circuit switched communications technologies, such as andwithout limitation, Wide Area Networks (WAN), such as the Internet,Local Area Networks (LAN), Public Switched Telephone Networks (PSTN),Plain Old Telephone Service (POTS), cellular communications networkssuch as a 3G/4G/5G or other cellular network, Internet of Things (IoT)networks, Cloud based networks, private networks, public networks, orotherwise.

The network 106 may utilize mid-band and/or high band 5G communicationsfrequencies. As is commonly known and appreciated, mid-band 5Gcommunications frequencies typically support communications of 100-400Mb/s download and are typically deployed over 2.4 GHz to 4.2 GHzfrequencies. Likewise, high band 5G communications frequencies typicallysupport communications of 1-2 Gb/s download and are typically deployedover 24-72 GHz frequencies.

One or more communications and networking standards and/or protocols maybe used including, without limitation, the TCP/IP suite of protocols,the Extensible Message and Presence Protocol (XMPP), VOIP, Ethernet,Wi-Fi, CDMA, GSM/GRPS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, 5G, MPEG, andothers.

As shown in FIG. 1 , one or more communications links may be establishedbetween nodes 102, the VNO server 104, and the database(s) 108. It is tobe appreciated that any combination of communications links may becombined or provided as single, multiple or other combinations ofcommunication links. Accordingly, it is to be appreciated that thecommunications links are described herein for purposes of functionalexplanation and are not limited to any particular physicalconfigurations.

A first node 102-1 may establish a first node link 112 with the VNOserver 104. The first node link 102-1 may be used to facilitatecommunication of Needs and Solutions by and between the first node 102-1and the VNO server 104.

A second node link 118-2/N may be established with the VNO server 104.The second node link 118-2/N may be used to facilitate communication ofNeeds and Solutions by and between one or more second nodes node 102-2/Nand the VNO server 104. The second node link 118-2/N may be optional andmay not be used in addition to the first node link 112. The first nodelink 112 is commonly used for an implementation of the presentdisclosure.

As further shown in FIG. 1 , a first node 102 may establish a data link120 with the one or more second nodes 102-2/N. The data link 120 may beused to facilitate communication of data between nodes over virtualnetwork connections orchestrated by the VNO server 104 and by thenetwork function virtualization infrastructure 110.

Database(s) 108

As shown in FIG. 1 , the system 100 may include one or more databases108. The databases 108 may be provided on the Cloud, one or more VNOservers 104, on one or more nodes 102, and/or otherwise. The databases108 provide data storage of data and information relevant the processingof Needs and Solutions. Such data may be replicated, in whole or inpart, on a server data storage 204, on a node data storage 304, orotherwise.

For at least one implementation, the database 108 may be utilized as arepository for “resource data” useful in monitoring network resources,including physical and/or virtual resources, tools available formanaging such network resources, and other data. For at least oneimplementation, such resource data may be accessible by a VNO server104, and more specifically, by an AIML engine 20B in identifyingSolutions to Needs.

For at least one implementation, resource data stored by the database108 or otherwise may be utilized to facilitate the arbitrage, trading,selling, leasing or otherwise of physical and/or virtual networkresources. By analogy, resource data may be useful in leasing, sellingor otherwise transacting with respect to, physical and/or virtualnetwork resources in a manner similar to the trading of futures, calls,puts, or the like in commodities, such as corn, beef, pigs, steel, bitcoins, currencies, or otherwise. Accordingly, and for at least oneimplementation, Solution data and Need data may be packaged by operatorsof VNO servers 104, nodes 104, or otherwise into tradable products onmarket exchanges, wherein the purchaser of such a package may acquirethe right to use one or more network resources (physical or virtual), atone or more places and/or times, and while having one or more SLRssatisfied during such use of the network resource(s).

For at least one implementation, a Need may include any need for anydata, product, service, or otherwise. For example, a Need may identify aneed for use of a car service, an airplane trip, or otherwise.Accordingly, the Need engine 302A may be configured to identify suchneeds and acquire Solutions, from VNO server(s) 204 to such needs andfrom one or more providers thereof. A VNO server 104 may be configuredto operate as a broker, intermediary, agent, or otherwise with respectto the providing of solutions to needs, where the solutions are providedby third parties and not by the VNO server 104.

Although various implementations have been described above with acertain degree of particularity, or with reference to one or moreindividual implementations, those skilled in the art could make numerousalterations to the disclosed implementations without departing from thespirit or scope of the present disclosure. The use of the terms“approximately” or “substantially” means that a value of an element hasa parameter that is expected to be close to a stated value or position.As is well known in the art, there may be minor variations that preventthe values from being exactly as stated. Accordingly, anticipatedvariances, such as 10% differences, are reasonable variances that aperson having ordinary skill in the art would expect and know areacceptable relative to a stated or ideal goal for one or moreembodiments of the present disclosure. It is also to be appreciated thatthe terms “top” and “bottom”, “left” and “right”, “up” or “down”,“first”, “second”, “next”, “last”, “before”, “after”, and other similarterms are used for description and ease of reference purposes and arenot intended to be limiting to any orientation or configuration of anyelements or sequences of operations for the various embodiments of thepresent disclosure. Further, the terms “coupled”, “connected” orotherwise are not intended to limit such interactions and communicationof signals between two or more devices, systems, components or otherwiseto direct interactions; indirect couplings and connections may alsooccur. Further, the terms “and” and “or” are not intended to be used ina limiting or expansive nature and cover any possible range ofcombinations of elements and operations of an implementation of thepresent disclosure. Other implementations are therefore contemplated. Itis intended that matter contained in the above description and shown inthe accompanying drawings shall be interpreted as illustrative ofembodiments and not limiting. Changes in detail or structure may be madewithout departing from the basic elements of the present disclosure asdefined in the following claims.

What is claimed is:
 1. A system, for customer specific network slicing,comprising: a VNO server; a first node; and a virtualized network;wherein the VNO server executes first computer instructionsinstantiating a solution manager engine which: identifies a Solution;communicates the Solution to the first node; and upon acceptance of theSolution by the first node, instructs the virtualized network to couplethe first node with a second node in accordance with the Solution. 2.The system of claim 1, wherein the virtualized network further comprisesnetwork function virtualization infrastructure; and wherein the Solutionincludes a slice of the virtualized network.
 3. The system of claim 2,wherein the Solution provides the slice which satisfies a Service LevelRequirement (SLR).
 4. The system of claim 3, wherein the SLR specifies amaximum latency for the slice.
 5. The system of claim 4, wherein the SLRis specified in a Need received by the VNO server from the first node.6. The system of claim 4, wherein the SLR is determined based upon anapplication program the first Node is at least one of currentlyexecuting and expected to later execute.
 7. The system of claim 6,wherein the application program specifies at least one of a dataprocessing requirement and a data communication requirement.
 8. Thesystem of claim 7, wherein the application program facilitates daytrading.
 9. The system of claim 7, wherein the application programfacilitates real-time sports betting.
 10. The system of claim 1, whereinthe VNO server executes second computer instructions instantiating anArtificial Intelligence/Machine Learning (AIML) engine which: monitorsthe Solution; monitors the first node for a requested Need; andgenerates a future Solution to a future Need.
 11. The system of claim10, wherein the AIML engine identifies gaps in the virtualized networkbased upon at least one of the Solution, a past Solution, a futureSolution, the requested Need, a past Need, and the future Need.
 12. Thesystem of claim 1, wherein the solution manager engine identifies afuture Need based upon an application program the first Node is at leastone of currently executing and expected to later execute.
 13. A node,for use with a customer specific network slicing system, comprising: acentral processing unit (CPU); wherein the CPU executes computerinstructions instantiating a need engine which: generates a Need;communicates the Need to a VNO server; receives a Solution to the Needfrom the VNO server; and communicates at least one of an acceptance, arejection, and a revised Solution to the VNO server.
 14. The node ofclaim 13, wherein the Need identifies at least one Service LevelRequirement (SLR) for a communicative coupling of the node with a secondnode over a virtualized network.
 15. The node of claim 14, wherein theSolution identifies a slice of the virtualized network; and wherein theSolution identifies whether the SLR identified in the Need can besatisfied by the slice of the virtualized network.
 16. The node of claim15, wherein the SLR is a bandwidth requirement.
 17. The node of claim16, wherein the bandwidth requirement arise with respect to atelemedicine application.
 18. A method for allocating virtualizednetwork resources comprising: receiving, at a VNO server and from afirst node, a Need request; determining whether the Need request can besatisfied by a present Solution; if the Need request can be satisfied bythe present Solution, assigning the present Solution to the first node;and communicatively coupling the first node with at least one secondnode using a slice of a virtualized network specified by the presentSolution; and if the Need request cannot be satisfied by the presentSolution, generating a new Solution.
 19. The method of claim 18, whereinthe Need request identifies a Service Level Requirement (SLR); whereinthe present Solution satisfies the SLR; and wherein the new Solutionidentifies at least one alternative to the SLR.
 20. The method of claim19, wherein the SLR specifies at least one of a maximum latency, abandwidth, a security requirement, and a routing requirement.